home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Geek Gadgets 2
/
Geek_Gadgets_2_2352.bin
/
lists
/
ade-gcc.archive.9602.gz
/
ade-gcc.archive.9602
/
000103_owner-ade-gcc_Wed Feb 21 12:53:45 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-02-28
|
1KB
Return-Path: <owner-ade-gcc>
Received: by fishpond (Smail3.1.29.1 #57)
id m0tpIjQ-000gXga; Wed, 21 Feb 96 12:53 EST
Sender: owner-ade-gcc
Received: by fishpond (Smail3.1.29.1 #57)
id m0tpIjM-000gXfC; Wed, 21 Feb 96 10:53 MST
Message-Id: <m0tpIjM-000gXfC@fishpond>
From: fnf (Fred Fish)
Subject: Re: GCC 2.7.2 patches
To: ade-gcc@ninemoons.com
Date: Wed, 21 Feb 1996 10:53:31 -0700 (MST)
In-Reply-To: <199602211554.PAA04758@mostar.nmrc.ucc.ie> from "Lars Hecking" at Feb 21, 96 03:54:53 pm
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 720
Sender: owner-ade-gcc@ninemoons.com
Precedence: bulk
> I'd recommend the unified diff format, because it's more compact, maybe
> slightly more difficult to read.
I used the unified format for these diffs, but not so much because it is more
compact. When you gzip the file, the duplication is essentially compressed
away (which is why compression works in the first place). I.E. if you gzip
a normal diff -c and a unified diff, the resulting file sizes should be very
comparable, even though the uncompressed diff -c will be much larger.
I like the unified diff format because it puts the changes in close proximity
with each other, which actually makes reading them a little easier when you
are trying to see what changed, especially for single line changes.
-Fred